Package | hl7.terminology |
Type | ImplementationGuide |
Id | Id |
FHIR Version | R5 |
Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/index.html |
Url | http://terminology.hl7.org/ImplementationGuide/hl7.terminology |
Version | 6.1.0 |
Status | active |
Date | 2024-11-19T17:21:55+00:00 |
Name | HL7Terminology |
Title | HL7 Terminology (THO) |
Experimental | False |
Realm | uv |
Authority | hl7 |
Description | Defines and exposes all HL7 terminologies managed through the unified terminology governance process |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: ImplementationGuide hl7.terminology
The official URL for this implementation guide is:
http://terminology.hl7.org/ImplementationGuide/hl7.terminology
Defines and exposes all HL7 terminologies managed through the unified terminology governance process
{
"resourceType" : "ImplementationGuide",
"id" : "hl7.terminology",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ImplementationGuide hl7.terminology</b></p><a name=\"hl7.terminology\"> </a><a name=\"hchl7.terminology\"> </a><a name=\"hl7.terminology-en-US\"> </a><h2>HL7Terminology</h2><p>The official URL for this implementation guide is: </p><pre>http://terminology.hl7.org/ImplementationGuide/hl7.terminology</pre><div><p>Defines and exposes all HL7 terminologies managed through the unified terminology governance process</p>\n</div></div>"
},
"url" : "http://terminology.hl7.org/ImplementationGuide/hl7.terminology",
"version" : "6.1.0",
"name" : "HL7Terminology",
"title" : "HL7 Terminology (THO)",
"status" : "active",
"experimental" : false,
"date" : "2024-11-19T17:21:55+00:00",
"publisher" : "HL7 International - Vocabulary Work Group",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org/Special/committees/vocab"
}
]
}
],
"description" : "Defines and exposes all HL7 terminologies managed through the unified terminology governance process",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001"
}
]
}
],
"packageId" : "hl7.terminology",
"license" : "CC0-1.0",
"fhirVersion" : [
"5.0.0"
],
"dependsOn" : [
{
"id" : "hl7ext",
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/implementationguide-dependency-comment",
"valueMarkdown" : "Automatically added as a dependency - all IGs depend on the HL7 Extension Pack"
}
],
"uri" : "http://hl7.org/fhir/extensions/ImplementationGuide/hl7.fhir.uv.extensions",
"packageId" : "hl7.fhir.uv.extensions.r5",
"version" : "5.1.0"
}
],
"definition" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/ig-internal-dependency",
"valueCode" : "hl7.fhir.uv.tools.r5#0.3.0"
}
],
"resource" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-assocConceptProp"
},
"name" : "MIF Associated concept property",
"description" : "Concept Properties that are associated with this Code System or Value Set Version"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-isNavigable"
},
"name" : "MIF concept relationship is navigable",
"description" : "Indicates whether the relationship is intended to be navigated when selecting a code"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-reflexivity"
},
"name" : "MIF concept relationship is reflexivity",
"description" : "Indicates if the association always holds for a concept with itself (refexive), never holds for a concept with itself (irreflexive)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-inverseName"
},
"name" : "MIF concept relationship inverse name",
"description" : "Identifies the name of the relationship that references the inverse of the current relationship. Allows linking a relationship and its derived inverse."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-relationshipKind"
},
"name" : "MIF concept relationship kind",
"description" : "Identifies a type of relationship between codes that is supported by this code system version"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-symmetry"
},
"name" : "MIF concept relationship symmetry",
"description" : "Indicates if the relationship always holds in the reverse direction as well (symetric), never holds in the reverse direction as well (antisymetric)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-mif-relationship-transitivity"
},
"name" : "MIF concept relationship transitivity",
"description" : "Indicates whether the relationship always (transitive) or never (antitransitive) propagates such that if the association exists from A to B and from B to C that the relationship can be inferred to exist from A to C"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-namingsystem-title"
},
"name" : "NamingSystem title",
"description" : "The human-readable descriptive name for the code or identifier system"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "StructureDefinition:extension"
}
],
"reference" : {
"reference" : "StructureDefinition/ext-namingsystem-version"
},
"name" : "NamingSystem version",
"description" : "The business version associated with the Naming System"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/cda-Rendering"
},
"name" : "CDA Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/deprCSVS-Rendering"
},
"name" : "Deprecated Code Systems Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/extallcontent-Rendering"
},
"name" : "Externals With Complete Content Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/extcsmetadatarecords-Rendering"
},
"name" : "External Code System Metadata Records Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/extwcontent-Rendering"
},
"name" : "Externals With Content Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/fhir-Normative"
},
"name" : "FHIR Normative Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/fhir-Rendering"
},
"name" : "FHIR Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/identifiers-Rendering"
},
"name" : "Identifier Systems Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/pendingCS-Rendering"
},
"name" : "Pending Code Systems Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/retired-Rendering"
},
"name" : "Retired Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/retired-extcsmetadatarecords-Rendering"
},
"name" : "Retired Code System Metadata Records Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/retired-extwcontent-Rendering"
},
"name" : "Retired Code System Fragments Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/retired-techids-Rendering"
},
"name" : "Retired Code System Identification Records Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/retiredExt-Rendering"
},
"name" : "Retired Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/techids-Rendering"
},
"name" : "Code System Identification Records Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/unified-Rendering"
},
"name" : "Unified Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/v2-Publishing"
},
"name" : "V2 Publishing Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/v2-rendering"
},
"name" : "V2 Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/v3-Publishing"
},
"name" : "V3 Publishing Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "List"
}
],
"reference" : {
"reference" : "List/v3-rendering"
},
"name" : "V3 Rendering Manifest"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ADAAreaOralCavitySystem"
},
"name" : "American Dental Association Area of Oral Cavity System",
"description" : "The Area of Oral Cavity System is accepted and approved by the ADA and is the most commonly used system used by dental professionals in America.\r\n\r\nArea of the oral cavity is designated by a two-digit code.\r\n\r\nThe Area of Oral Cavity System can be found in the ADA Comprehensive ADA Dental Claim Form Completion Instructions (see https://www.ada.org/-/media/project/ada-organization/ada/ada-org/files/publications/cdt/v2019adadentalclaimcompletioninstructions_v3_2022feb.pdf). For more information see here: https://www.ada.org/publications/cdt/ada-dental-claim-form. \r\n\r\nA Statement of Understanding (SOU) between ADA and HL7 exists here: http://www.hl7.org/documentcenter/public/mou/ADA%20HL7%20SOU%202021_signed.pdf"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ADAToothSurfaceCodes"
},
"name" : "ADA Tooth Surface Codes",
"description" : "Tooth Surface Codes are defined by the HIPAA standard electronic dental claim transaction (837D v5010) and the ADA Dental Claim Form. Surface codes can be used in a variety of combinations to define a multi-surface procedure (ie. MOD for a singular intervention which covers Mesial, Occlusal, and Distal surfaces). Tooth Surface Codes can be accessed through the [ADA Guide to Dental Procedures Reported with Area of the Oral Cavity or Tooth Anatomy (or Both).](https://www.ada.org/-/media/project/ada-organization/ada/ada-org/files/publications/cdt/final_areaoftheoralcavityandtoothanatomy.pdf?rev=fbd215c7d8c546aa967443e79f9d8e20&hash=2F759947EFD75EF5ABCCBF0F62CE1FE7)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ADAUniversalToothDesignationSystem"
},
"name" : "ADA Universal Tooth Designation System",
"description" : "The American Dental Association (ADA) accepted the Universal/National Tooth Designation System and the ISO/ANSI/ADA Specification No. 3950 for Designation System for Teeth and Areas of the Oral Cavity as the human tooth and oral cavity enumeration schemas in 1994.\r\n\r\nThe universal tooth designation or numbering system is accepted and approved by the ADA and is the most commonly used system used by dental professionals in America.\r\n\r\nTeeth are numbered 1-32, starting with the third molar (1) on the right side of the upper arch, following around the arch to the third molar (16) on the left side, and descending to the lower third molar (17) on the left side, and following that arch to the terminus of the lower jaw, the lower right third molar (32).\r\n\r\nSupernumerary teeth are identified by the numbers 51 through 82, beginning with the area of the upper right third molar, following around the upper arch and continuing on the lower arch to the area of the lower right third molar (e.g., supernumerary #51 is adjacent to the upper right molar #1; supernumerary #82 is adjacent to the lower right third molar #32).\r\n\r\nThe Universal Numbering System can be found in the ADA Dental Claim Form. For more information see here: https://www.ada.org/publications/cdt/ada-dental-claim-form. \r\n\r\nA Statement of Understanding (SOU) between ADA and HL7 exists here: http://www.hl7.org/documentcenter/public/mou/ADA%20HL7%20SOU%202021_signed.pdf"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCConditionCodes"
},
"name" : "AHA NUBC Condition Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 18-28 Condition Codes\r\n\r\nThese codes are used to convey the applicable Condition Codes and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nNational Uniform Billing Committee Data Element Specifications Change Request Guidelines\r\n\r\n\"The National Uniform Billing Committee (NUBC) holds meetings and conference calls throughout the year and change requests to the UB-04 Manual or UB-04 Data Set may be submitted at any time. To be considered at the next scheduled meeting, requests for changes must be received by the NUBC Secretary at least 45 days in advance. Approved changes are usually effective as of July 1 or about 90 days after approval, as appropriate.\"\r\n\r\nFor more information and to submit a change request, please see [here](https://www.nubc.org/form/change-request-guidelines-form-n)\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCPatientDischargeStatus"
},
"name" : "AHA NUBC Patient Discharge Status Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 17 - Patient Discharge Status\r\n\r\nThese codes are used to convey the patient discharge status and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCPointOfOriginNewborn"
},
"name" : "AHA NUBC Point of Origin for Newborn",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 15 - Point of Origin for Admission or Visit for Newborn\r\n\r\nThese codes are used to convey the patient point of origin for an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCPointOfOriginNonnewborn"
},
"name" : "AHA NUBC Point of Origin for Non-newborn",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 15 - Point of Origin for Admission or Visit for Non-newborn\r\n\r\nThese codes are used to convey the patient point of origin for an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCPriorityTypeOfAdmitOrVisit"
},
"name" : "AHA NUBC Priority (Type) of Admission or Visit",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 14 - Priority (Type) of Admission or Visit\r\n\r\nThese codes are used to convey the priority of an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCRevenueCodes"
},
"name" : "AHA NUBC Revenue Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 42 - Revenue Codes\r\n\r\nThese codes are used to convey the revenue code and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCTypeOfBill"
},
"name" : "AHA NUBC Type Of Bill Codes",
"description" : "The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\r\n\r\nThis code system consists of the following:\r\n\r\n \\* FL 04 - Type of Bill Facility Codes\r\n\r\n \\* FL 04 - Type of Bill Frequency Codes\r\n\r\nA code indicating the specific Type of Bill (TOB), e.g., hospital inpatient, outpatient, replacements, voids, etc. The first digit is a leading zero*. The fourth digit defines the frequency of the bill for the institutional and electronic professional claim.\r\n\r\nNote that with the advent of UB-04, the matrix methodology of constructing the first component of TOB codes according to digit position was abandoned in favor of specifying valid discrete codes. As a result, the first three digits in TOB have no underlying meaning.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nThe UB-04 Manual has a 12-month subscription period from June 30 through July 1."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/AHANUBCValueCodesAndAmounts"
},
"name" : "AHA NUBC Value Codes and Amounts",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 39-41 Value Codes and Amounts\r\n\r\nThese codes are used to convey the applicable Value Codes and Amounts and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nNational Uniform Billing Committee Data Element Specifications Change Request Guidelines\r\n\r\n\"The National Uniform Billing Committee (NUBC) holds meetings and conference calls throughout the year and change requests to the UB-04 Manual or UB-04 Data Set may be submitted at any time. To be considered at the next scheduled meeting, requests for changes must be received by the NUBC Secretary at least 45 days in advance. Approved changes are usually effective as of July 1 or about 90 days after approval, as appropriate.\"\r\n\r\nFor more information and to submit a change request, please see [here](https://www.nubc.org/form/change-request-guidelines-form-n)\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/APDRG"
},
"name" : "All Patient Diagnosis Related Groups (AP DRGs)",
"description" : "In 1987, the state of New York passed legislation instituting a DRG-based prospective payment system for all non-Medicare patients. The legislation included a requirement that the New York State Department of Health (NYDH) evaluate the applicability of the DRGs to a non-Medicare population. In particular, the legislation required that the DRGs be evaluated with respect to neonates and patients with Human Immunodeficiency Virus (HIV) infections. NYDH entered into an agreement with 3M HIS to assist with the evaluation of the need for DRG modifications as well as to make the necessary changes in the DRG definitions and software. The DRG definitions developed by NYDH and 3M HIS are referred to as the All Patient DRGs (AP DRGs)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/APRDRG"
},
"name" : "All Patient Refined Diagnosis Related Groups (APR DRGs)",
"description" : "3M APR DRGs have become the standard across the U.S. for classifying hospital inpatients in non-Medicare populations. As of January 2019, 27 state Medicaid programs use 3M APR DRGs to pay hospitals, as do approximately a dozen commercial payers and Medicaid managed care organizations. Over 2,400 hospitals have licensed 3M APR DRGs to verify payment and analyze their internal operations.\r\n\r\nThe 3M APR DRG methodology classifies hospital inpatients according to their reason for admission, severity of illness and risk of mortality.\r\n\r\nEach year 3M calculates and releases a set of statistics for each 3M APR DRG based on our analysis of large national data sets. These statistics include a relative weight for each 3M APR DRG. The relative weight reflects the average hospital resource use for a patient in that 3M APR DRG relative to the average hospital resource use of all inpatients. Please note that payers and other users of the 3M APR DRG methodology are responsible for ensuring that they use relative weights that are appropriate for their particular populations. The 3M APR DRG statistics also include data for each 3M APR DRG on relative frequency, average length of stay, average charges and incidence of mortality.\r\n\r\n3M APR DRGs can be rolled up into broader categories. The 326 base DRGs roll up into 25 major diagnostic categories (MDCs) plus a pre-MDC category. An example is MDC 04, Diseases and Disorders of the Respiratory System. As well, each 3M APR DRG is assigned to a service line that is consistent with the outpatient service lines that are defined by the 3M⢠Enhanced Ambulatory Patient Groups (EAPGs)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CAPeCC"
},
"name" : "College of American Pathologists (CAP) eCC (electronic Cancer Checklists)",
"description" : "\"The College of American Pathologists (CAP) eCC (electronic Cancer Checklists) enables pathologists to use the [CAP Cancer Protocols](https://www.cap.org/protocols-and-guidelines/cancer-reporting-tools/cancer-protocols) directly within their laboratory information system (LIS) workflow and to ensure that each report is completed with the necessary required elements. Most anatomic pathology (AP)-LIS vendors offer a CAP eCC synoptic module for reporting on surgical cancer resections and selected biopsies.\"\r\n\r\n\"The CAP eCC is based on the [CAP Cancer Protocols](https://www.cap.org/protocols-and-guidelines/cancer-reporting-tools/cancer-protocols) and is produced under the guidance of the [CAP Pathology Electronic Reporting (PERT) Committee](https://www.cap.org/member-resources/councils-committees/pathology-electronic-reporting-pert-committee) along with close interaction and advisement of the [Cancer Committee](https://www.cap.org/member-resources/councils-committees/cancer-committee).\r\n\r\nThe eCC is developed in collaboration with and partially underwritten by the Centers for Disease Control and Prevention (CDC). Additional collaborators include the American Joint Committee on Cancer (AJCC), Cancer Care Ontario (CCO), and the North American Association of Central Cancer Registries (NAACCR).\r\n\r\nThe CAP currently is working with the [California Cancer Registry (CCR)](http://www.ccrcal.org/) to offer the benefits of the eCC to California laboratories. CCR and the CAP are seeking out laboratories interested in participating in an ongoing project using the eCC to directly transfer cancer data to the central registry.\"\r\n\r\n\"The CAP releases eCC templates on a rolling basis, coordinating as much as possible with the posting of new and revised [Cancer Protocols and Cancer Biomarker Reporting Templates](https://www.cap.org/protocols-and-guidelines/cancer-reporting-tools/cancer-protocol-templates). A few weeks prior to each Major or Agile release, email notifications are sent out to all licensed CAP eCC users.\" For more information, see page [here](https://www.cap.org/laboratory-improvement/proficiency-testing/cap-ecc)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/hc-CCDD"
},
"name" : "Canadian Clinical Drug Data Set",
"description" : "The Canadian Clinical Drug Data Set provides codes for identification and a consistent approach to naming of medications and some medical devices in Canada. It has been designed and developed to reflect current clinical practice and safety advice and is freely available for use in digital health solutions and design applications. CCDD is available in English and Canadian French.\r\n\r\nTo request content changes, send an email to [clinicaldrug@infoway-inforoute.ca](mailto:clinicaldrug@infoway-inforoute.ca).\r\n\r\nCanada Health Infoway has developed a FHIR representation of CCDD, which can be viewed at: [https://ontoserver.csiro.au/shrimp/launch.html?iss=https://terminologystandardsservice.ca/fhir](https://ontoserver.csiro.au/shrimp/launch.html?iss=https://terminologystandardsservice.ca/fhir)\r\n\r\nThe CCDD FHIR representation contains supplemental property codes, as defined in the Health Canada Drug Product Database (DPD), managed by Health Canada, as follows:\r\n\r\n- Anatomical Therapeutical Chemical (ATC): The purpose of the ATC classification system is to be used as a tool for drug utilization research to improve the quality of drug use.\r\n\r\n- Biosimilar: Identifies biosimilar products.\r\n\r\n- Pediatric: Identifies pediatric products.\r\n\r\n- Schedule: Each drug is assigned one or more schedules according to the Food and Drug Regulations and the Controlled Drugs and Substances Act.\r\n\r\nFurther information on the supplemental properties may be obtained by reviewing the information at [https://www.canada.ca/en/health-canada/services/drugs-health-products/drug-products/drug-product-database.html](https://www.canada.ca/en/health-canada/services/drugs-health-products/drug-products/drug-product-database.html) or by emailing [pharma_drug_enquiries-renseignements_medicaments_pharma@hc-sc.gc.ca](mailto:pharma_drug_enquiries-renseignements_medicaments_pharma@hc-sc.gc.ca)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CDCLocal"
},
"name" : "CDC Local Coding System",
"description" : "\"CDC Public Health Information Network local coding system used for creating the concepts that are not available in the Standard Development Organization (SDO) Vocabulary like SNOMED CT, LOINC, ICD-9, etc.\"\r\n\r\nVersioning numbered according to PHIN VADS convention.\r\n\r\nFor more information, see [https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.114222.4.5.274](https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.114222.4.5.274)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CDCREC"
},
"name" : "CDC Race and Ethnicity",
"description" : "The U.S. Centers for Disease Control and Prevention (CDC) has prepared a code set for use in coding race and ethnicity data. This code set is based on current federal standards for classifying data on race and ethnicity, specifically the minimum race and ethnicity categories defined by the U.S. Office of Management and Budget (OMB) and a more detailed set of race and ethnicity categories maintained by the U.S. Bureau of the Census (BC). The main purpose of the code set is to facilitate use of federal standards for classifying data on race and ethnicity when these data are exchanged, stored, retrieved, or analyzed in electronic form. At the same time, the code set can be applied to paper-based record systems to the extent that these systems are used to collect, maintain, and report data on race and ethnicity in accordance with current federal standards.\r\n\r\nThe content is available at https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.113883.6.238#."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CDPS"
},
"name" : "Chronic Illness and Disability Payment System (CDPS)",
"description" : "\"The Chronic Illness and Disability Payment System (CDPS) is a diagnostic-based risk adjustment model that is widely used to adjust capitated payments for health plans that enroll Medicaid beneficiaries.\r\n\r\nCDPS uses International Classification of Disease (ICD) codes to assign CDPS Categories that indicate illness burden related to major body systems (e.g. cardiovascular) or types of chronic disease (e.g. diabetes). Within each major category is a hierarchy reflecting both the clinical severity of the condition and its expected effect on future costs. Each of the hierarchical CDPS Categories is assigned a CDPS weight. CDPS weights are additive across major categories.\"\r\n\r\n\"The CDPS model was developed in 2000 using data from seven Fee-for-Service (FFS) Medicaid programs. The model received major updates in 2009 (using national FFS Medicaid data from 2002-2005) and in 2014 (using additional national FFS Medicaid data from 2011). CDPS has also received regular annual updates to include the most recent ICD and NDC codes.\"\r\n\r\nFor more information, please visit [https://hwsph.ucsd.edu/research/programs-groups/cdps.html](https://hwsph.ucsd.edu/research/programs-groups/cdps.html)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CDT"
},
"name" : "Code on Dental Procedures and Nomenclature",
"description" : "The purpose of the CDT Code is to achieve uniformity, consistency and specificity in accurately documenting dental treatment. One use of the CDT Code is to provide for the efficient processing of dental claims, and another is to populate an Electronic Health Record."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CMSPlaceofServiceCodes"
},
"name" : "CMS Place of Service Codes (POS)",
"description" : "Place of Service Codes are two-digit codes placed on health care professional claims to indicate the setting in which a service was provided. The Centers for Medicare & Medicaid Services (CMS) maintain POS codes used throughout the health care industry.\r\n\r\nThis code set is required for use in the implementation guide adopted as the national standard for electronic transmission of professional health care claims under the provisions of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). HIPAA directed the Secretary of HHS to adopt national standards for electronic transactions. These standard transactions require all health plans and providers to use standard code sets to populate data elements in each transaction. The Transaction and Code Set Rule adopted the ASC X12N-837 Health Care Claim: Professional, volumes 1 and 2, as the standard for electronic submission of professional claims. This standard names the POS code set currently maintained by CMS as the code set to be used for describing sites of service in such claims. POS information is often needed to determine the acceptability of direct billing of Medicare, Medicaid and private insurance services provided by a given provider."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/cmsrxhcc"
},
"name" : "CMS Prescription Drug Hierarchical Condition Categories",
"description" : "Starting in 2006, with the implementation of the Part D program, CMS introduced a second major HCC-based risk adjustment model. Created with the passage of the Medicare Modernization Act (MMA) of 2003, the Medicare Part D Prescription Drug benefit became the second major Medicare capitated payment system. CMS developed the Part D RxHCC risk adjustment model to apply to monthly capitated payments to both Medicare Advantage (MA-PDs) and standalone prescription drug plans (PDPs). The Part D RxHCC risk adjustment model implemented in 2006 was developed using a structure similar to the CMS-HCC model, in that it included demographic and diagnosis information clustered into hierarchical condition categories. CMS obtains diagnoses for all Medicare beneficiaries from either fee-for-service claims or Medicare Advantage reporting. In 2011, CMS implemented an updated Part D RxHCC risk adjustment model, incorporating program data derived from prescription drug event (PDE) data. The data used to calibrate this updated model was more recent cost and utilization data, resulting in a model that reflects more recent drug cost and utilization patterns.\r\n\r\nFor more information, see: https://www.cms.gov/Medicare/Health-Plans/MedicareAdvtgSpecRateStats/Risk-Adjustors\r\n\r\nThe CMS RxHCCs are in the public domain and are free to use without restriction."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CPT"
},
"name" : "Current Procedural Terminology (CPT®)",
"description" : "The Current Procedural Terminology (CPT) code set, created and maintained by the American Medical Association, is the language of medicine today and the code to its future. This system of terminology is the most widely accepted medical nomenclature used to report medical procedures and services under public and private health insurance programs. CPT coding is also used for administrative management purposes such as claims processing and developing guidelines for medical care review. Each year, via a rigorous, evidence-based and transparent process, the independent CPT Editorial Panel revises, creates or deletes hundreds of codes in order to reflect current medical practice.\r\n\r\nDesignated by the U.S. Department of Health and Human Services under the Health Insurance Portability and Accountability Act (HIPAA) as a national coding set for physician and other health care professional services and procedures, CPTâs evidence-based codes accurately encompass the full range of health care services.\r\n\r\nAll CPT codes are five-digits and can be either numeric or alphanumeric, depending on the category. CPT code descriptors are clinically focused and utilize common standards so that a diverse set of users can have common understanding across the clinical health care paradigm.\r\n\r\nThere are various types of CPT codes:\r\n\r\nCategory I: These codes have descriptors that correspond to a procedure or service. Codes range from 00100â99499 and are generally ordered into sub-categories based on procedure/service type and anatomy.\r\n\r\nCategory II: These alphanumeric tracking codes are supplemental codes used for performance measurement. Using them is optional and not required for correct coding.\r\n\r\nCategory III: These are temporary alphanumeric codes for new and developing technology, procedures and services. They were created for data collection, assessment and in some instances, payment of new services and procedures that currently donât meet the criteria for a Category I code.\r\n\r\nProprietary Laboratory Analyses (PLA) codes: These codes describe proprietary clinical laboratory analyses and can be either provided by a single (âsolesourceâ) laboratory or licensed or marketed to multiple providing laboratories that are cleared or approved by the Food and Drug Administration (FDA)). This category includes but is not limited to Advanced Diagnostic Laboratory Tests (ADLTs) and Clinical Diagnostic Laboratory Tests (CDLTs), as defined under the Protecting Access to Medicare Act of 2014 (PAMA)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CVX"
},
"name" : "Vaccine Administered Code Set (CVX)",
"description" : "The CDC's National Center of Immunization and Respiratory Diseases (NCIRD - see [https://www.cdc.gov/ncird/](https://www.cdc.gov/ncird/)) developed and maintains the CVX (vaccine administered) code set. It includes both active and inactive vaccines available in the US. CVX codes for inactive vaccines allow transmission of historical immunization records. When a MVX (manufacturer) code is paired with a CVX (vaccine administered) code, the specific trade named vaccine may be indicated. These codes should be used for immunization messages using either HL7 Version 2.3.1 or HL7 Version 2.5.1. CVX is the underlying Master Code System for V2 table 0292 (Vaccines Administered). The machine readable name for CVX in PHIN VADS is PH_VaccinesAdministeredCVX_CDC_NIP. The version of the CVX code set for certification can be found on the archive page:[https://www2a.cdc.gov/vaccines/iis/iisstandards/mu3versioned_codes.asp](https://www2a.cdc.gov/vaccines/iis/iisstandards/mu3versioned_codes.asp) \r\n\r\nThe Status column indicates if the vaccine is currently available in the United States.\r\n\r\n* Active: A currently available administrable vaccine \r\n\r\n* Inactive: An administrable vaccine formulation that is no longer available for patient administration, but can be found in historical patient records OR A historical record of a vaccine administered where the exact formulation is unknown \r\n\r\n* Pending: A vaccine that is expected to become active in the future \r\n\r\n* Non-US: A vaccine that available outside the US only \r\n\r\n* Never Active: A vaccine that was never available and is not in the pipeline of new vaccines \r\n\r\nThe Last Updated column indicates the last time this particular vaccine code was updated in this table.\r\n\r\nQuestions regarding this table should be directed to the IIS Technical Assistance Team via iisinfo@cdc.gov (or use mailing address via [https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cvx#addr](https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cvx#addr)) \r\n\r\nHL7 Implementers should note that 'Status' IS NOT CONCEPT STATUS as all codes are ACTIVE in this code system.\r\n\r\nThe current code system is available via [https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cvx](https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cvx)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/CanadaProvinceCodes"
},
"name" : "Canada Post Province Codes",
"description" : "For more information, see [https://www.canadapost-postescanada.ca/cpc/en/support/articles/addressing-guidelines/symbols-and-abbreviations.page](https://www.canadapost-postescanada.ca/cpc/en/support/articles/addressing-guidelines/symbols-and-abbreviations.page)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ClinicalTrialsGov"
},
"name" : "ClinicalTrials.gov",
"description" : "The U.S. National Institutes of Health, Department of Health and Human Services, through its National Library of Medicine, has developed [ClinicalTrials.gov](http://clinicaltrials.gov) to provide patients, family members, and members of the public current information about clinical research studies. [ClinicalTrials.gov](http://clinicaltrials.gov) contains summary information about clinical studies being conducted throughout the United States and in many countries throughout the world. These data are provided to the National Library of Medicine by organizations and institutions that sponsor and implement the studies.\r\n\r\n[ClinicalTrials.gov](http://clinicaltrials.gov) is updated daily. You should check [ClinicalTrials.gov](http://clinicaltrials.gov) frequently for updated information.\r\n\r\nMore information about ClinicalTrials.gov can be found [here](https://clinicaltrials.gov/about-site/about-ctg)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/FIPS52"
},
"name" : "Federal Information Processing Standards Publication: Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas (FIPS 5-2)",
"description" : "\"This standard provides a set of two-digit numeric codes and a set of two-letter alphabetic codes for representing the 50 states, the District of Columbia and the outlying areas of the United States, and associated areas. The standard covers all land areas under the sovereignty of the United States, the freely associated states of Federated States of Micronesia and Marshall Islands, and the trust territory of Palau. This revision supersedes FIPS PUB 5-1 in its entirety.\"\r\n\r\nFor more information, see [https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub5-2.pdf](https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub5-2.pdf)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/FIPS64"
},
"name" : "Federal Information Processing Standards Publication: Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas (FIPS 6-4)",
"description" : "\"The FIPS county code is a five-digit Federal Information Processing Standard (FIPS) code (FIPS 6-4) which uniquely identifies counties and county equivalents in the United States, certain U.S. possessions, and certain freely associated states. This is the 3-digit part of the 5-digit county FIPS code specifically standing for the county.\"\r\n\r\nFor more information, see [https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub6-4.pdf](https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub6-4.pdf)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/GTR"
},
"name" : "Genetic Testing Registry",
"description" : "The Genetic Testing Registry (GTR) provides a central location for voluntary submission of genetic test information by providers. The scope includes the test's purpose, methodology, validity, evidence of the test's usefulness, and laboratory contacts and credentials. The overarching goal of the GTR is to advance the public health and research into the genetic basis of health and disease.\r\n\r\nEach Test is a specific, orderable test from a particular laboratory, and is assigned a unique GTR accession number. The format is GTR00000001.1, with a leading prefix \"GTR\" followed by 8 digits, a period, then 1 or more digits representing the version. When a laboratory updates a registered test, a new version number is assigned.\r\n\r\nTo find all laboratories in GTR and all registered tests, see here https://www.ncbi.nlm.nih.gov/gtr/all/tests/?term=all%5Bsb%5D"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/HGNCGeneGroup"
},
"name" : "HUGO Gene Nomenclature Committee Gene Group",
"description" : "\"The HGNC is responsible for approving unique symbols and names for human loci, including protein coding genes, ncRNA genes and pseudogenes, to allow unambiguous scientific communication.\"\r\n\r\nHGNC Gene Group is an index on gene families/groups. The numeric GeneGroup IDs should be used as codes. GeneGroup IDs do not begin with \"HGNC:\" (like the GeneIDs for genes in HGNC Genes), so care must be made to ensure alignment of concepts when viewing an HGNC ID from an older system that may be referring to the GeneID and not a gene group. For example, 588 refers to the HLA gene family, but HGNC:588 identifies the ATG12 gene. To provide clarity for systems that do not distinguish codes from genes and gene families, use \"http://www.genenames.org\" for genes and \"http://www.genenames.org/genegroup\" for gene families as code system URIs.\r\n\r\n\"For each known human gene we approve a gene name and symbol (short-form abbreviation). All approved symbols are stored in the HGNC database,[www.genenames.org](https://www.genenames.org/tools/search), a curated online repository of HGNC-approved gene nomenclature, gene groups and associated resources including links to genomic, proteomic and phenotypic information. Each symbol is unique and we ensure that each gene is only given one approved gene symbol. It is necessary to provide a unique symbol for each gene so that we and others can talk about them, and this also facilitates electronic data retrieval from publications and databases.\"\r\n\r\nFor more information on the use of HGNC Genes, see [https://terminology.hl7.org/CodeSystem-v3-hgnc.html](https://terminology.hl7.org/CodeSystem-v3-hgnc.html).\r\n\r\nHGNC is a free database for the public.\r\n\r\nPlease see https://www.genenames.org/ for more info."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/HIPPS"
},
"name" : "Health Insurance Prospective Payment System (HIPPS)",
"description" : "\"Health Insurance Prospective Payment System (HIPPS) rate codes represent specific sets of patient characteristics (or case-mix groups) health insurers use to make payment determinations under several prospective payment systems. Case-mix groups are developed based on research into utilization patterns among various provider types. For the payment systems that use HIPPS codes, clinical assessment data is the basic input. A standard patient assessment instrument is interpreted by case-mix grouping software algorithms, which assign the case mix group. For payment purposes, at least one HIPPS code is defined to represent each case-mix group. These HIPPS codes are reported on claims to insurers.\r\n\r\nInstitutional providers use HIPPS codes on claims in association with special revenue codes. One revenue code is defined for each prospective payment system that requires HIPPS codes. HIPPS codes are placed in data element SV202 on the electronic 837 institutional claims transaction, using an HP qualifier, or in Form Locator (FL) 44 (\"HCPCS/rate\") on a paper UB-04 claims form. The associated revenue code is placed in data element SV201 or in FL 42. In certain circumstances, multiple HIPPS codes may appear on separate lines of a single claim.\"\r\n\r\n\"HIPPS codes are alpha-numeric codes of five digits. Each code contains intelligence, with certain positions of the code indicating the case mix group itself, and other positions providing additional information. The additional information varies among HIPPS codes pertaining to different payment systems, but often provides information about the clinical assessment used to arrive at the code. Which positions of the code carry the case mix group information may also vary by payment systems.\"\r\n\r\n\"Under the Health Insurance Portability and Accountability Act (HIPAA) rules for transactions and code sets, HIPPS codes are defined as a non-medical code set. Therefore, these codes are effective by transaction date.\r\n\r\nEffective From Dates: HIPPS codes are valid under HIPAA on transactions on or after this date. Since all HIPPS codes to date have been initially created for Original Medicare payment systems, this is also date of service the codes begin to be payable by Medicare. While it is valid under HIPAA rules that a claim for dates of service before this date could be submitted on a transaction after this date, CMS is not aware of a business need for a provider to do so. The code would not be payable by any insurer and no Grouper software would be available to produce a code for those dates.\r\n\r\nEffective Through Dates: HIPPS codes are no longer valid under HIPAA on transactions on or after this date. This date may vary from the date a code ceases to be payable by Medicare, since other payers may continue to use older HIPPS codes after Medicare transitions to a new payment system. Since CMS, as the HIPPS code set maintainer, may not have complete information about other payersâ uses of these codes, codes may remain effective under HIPAA long after they cease to be payable on Medicare claims. To reflect this, a separate column on the HIPPS Code Master List indicates the Medicare Payment Though Date.\""
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/HPO"
},
"name" : "Human Phenotype Ontology",
"description" : "\"The Human Phenotype Ontology (HPO) provides a standardized vocabulary of phenotypic abnormalities encountered in human disease. Each term in the HPO describes a phenotypic abnormality, such as Atrial septal defect. The HPO is currently being developed using the medical literature, Orphanet, DECIPHER, and OMIM. HPO currently contains over 13,000 terms and over 156,000 annotations to hereditary diseases. The HPO project and others have developed software for phenotype-driven differential diagnostics, genomic diagnostics, and translational research. The HPO is a flagship product of the Monarch Initiative, an NIH-supported international consortium dedicated to semantic integration of biomedical and model organism data with the ultimate goal of improving biomedical research. The HPO, as a part of the Monarch Initiative, is a central component of one of the 13 driver projects in the Global Alliance for Genomics and Health (GA4GH) strategic roadmap.\"\r\n\r\nPlease see https://hpo.jax.org/app/download/ontology.\r\n\r\nReleases, produced approximately every 2 months, can be found [here](https://github.com/obophenotype/human-phenotype-ontology/releases)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ca-hc-dpd-schedule"
},
"name" : "Health Canada Drug Product Database - Schedule",
"description" : "The Code System describes the characteristics of drugs for use in Canada.\r\n\r\nDrugs in Canada are assigned one or more of the following schedules, according to the Food and Drug Regulations, and the Controlled Drugs and Substances Act.\r\n\r\n- Prescription (prescription drugs included in the Prescription Drug List)\r\n\r\n- Prescription Recommended (drugs that are recommended to be listed on the Prescription Drug List)\r\n\r\n- Schedule G (control drugs)\r\n\r\n- Schedule G (Controlled Drugs and Substances Act [CDSA] III)\r\n\r\n- Schedule G (CDSA IV)\r\n\r\n- Schedule C (drugs listed in Schedule C of the Food and Drugs Act, for example, radiopharmaceutical drugs)\r\n\r\n- Schedule D (drugs listed in Schedule D of the Food and Drugs Act, ie. biological products)\r\n\r\n- Narcotic (Narcotic Control Act)\r\n\r\n- Narcotic (CDSA I)\r\n\r\n- Narcotic (CDSA II)\r\n\r\n- Targeted (CDSA IV)\r\n\r\n- CDSA Recommended- Undergoing Regulatory Amendment to add this new substance to Controlled Drugs Substances Act\r\n\r\n- OTC (over the counter drugs that do not appear on a schedule or are not recommended to appear on any schedule)\r\n\r\n- Ethical: a drug that, in accordance with Federal Legislation, does not require a prescription, but that is generally prescribed by a medical practitioner. Ethical products are unscheduled non-prescription professional use products (e.g. MRI contrast agents, hemodialysis solutions) and a few emergency use products (e.g. nitroglycerine)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/IANATimeZoneDatabase"
},
"name" : "IANA Time Zone Database",
"description" : "The Time Zone Database (often called tz or zoneinfo) contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/icaosex"
},
"name" : "International Civil Aviation Organization Sex",
"description" : "ICAO is funded and directed by 193 national governments to support their diplomacy and cooperation in air transport as signatory states to the [Chicago Convention (1944)](https://www.icao.int/about-icao/History/Pages/default.aspx)\r\n\r\nIts core function is to maintain an administrative and expert bureaucracy (the [ICAO Secretariat](https://www.icao.int/secretariat/Pages/default.aspx) supporting these diplomatic interactions, and to research new air transport policy and standardization innovations as directed and endorsed by governments through the [ICAO Assembly](https://www.icao.int/about-icao/assembly/Pages/default.aspx), or by the [ICAO Council](https://www.icao.int/about-icao/Council/Pages/council.aspx) which the assembly elects.\r\n\r\nICAO has developed a technical specification (sample version form 2021 [here](https://www.icao.int/publications/Documents/9303_p7_cons_en.pdf) ) to \"allow compatibility and global interchange using both visual (eye readable) and machine readable means. The specifications lay down standards for visas which can, where issued by a State and accepted by a receiving State, be used for travel purposes. The MRV[Machine Readable Visa] shall, as a minimum, contain the data specified herein in a form that is legible both visually and by optical character recognition methods..\" \r\n\r\nFurther, defining that \"Sex of MRV-A[Format A - Machine Readable Visa] holder, when included, is to be specified by use of the single initial commonly used in the language of the State of issue. If translation into English, French or Spanish is necessary, followed by an oblique and the capital letter F for female, M for male, or X for unspecified.\"\r\n\r\nSex of MRV-B[Format B - Machine Readable Visa] holder, when included, is to be specified by use of the single initial commonly used in the language of the State of issue. If translation into English, French or Spanish is necessary, followed by an oblique and the capital letter F for female, M for male, or X for unspecified."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ICD11MMS"
},
"name" : "International Classification of Diseases, 11th Revision Mortality and Morbidity Statistics (MMS)",
"description" : "The International Classification of Diseases, 11th Revision Mortality and Morbidity Statistics (MMS) is one of the ICD11 linearizations. Information about the ICD Foundation Component and the ICD11 Linearizations can be found in the complete reference guide here: [https://icd.who.int/icd11refguide/en/index.html](https://icd.who.int/icd11refguide/en/index.html)\r\n\r\n\"**The ICD11 Linearizations (Tabular lists)**\r\n\r\nA linearization is a subset of the foundation component, that is:\r\n\r\n1. fit for a particular purpose: reporting mortality, morbidity, primary care or other uses;\r\n\r\n 2. composed of entities that are Mutually Exclusive of each other; \r\n\r\n3. each entity is given a single parent.\r\n\r\nLinearization is similar to the classical print versions of ICD Tabular List (e.g. volume I of ICD-10 or other previous editions). The main linearization of ICD-11 is Mortality and Morbidity Statistics (MMS). Various linearizations could be built at different granularity, use case or other purposes such as for Primary Care, Clinical Care or Research. The linkage from the foundation component to a particular linearization will ensure consistent use of the ICD.\"\r\n\r\nICD-11 for Mortality and Morbidity (ICD-11 MMS) can be downloaded in either print or electronic (spreadsheet) format from the browser in the Info tab located [here](https://icd.who.int/browse11/l-m/en)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ICF"
},
"name" : "International Classification of Functioning, Disability and Health",
"description" : "\"The International Classification of Functioning, Disability and Health, known more commonly as ICF, is a classification of health and health-related domains. As the functioning and disability of an individual occurs in a context, ICF also includes a list of environmental factors.\r\n\r\nICF is the WHO framework for measuring health and disability at both individual and population levels.\r\n\r\nICF was officially endorsed by all 191 WHO Member States in the Fifty-fourth World Health Assembly on 22 May 2001(resolution [WHA 54.21](http://apps.who.int/gb/archive/pdf_files/WHA54/ea54r21.pdf) ) as the international standard to describe and measure health and disability.\r\n\r\nICF is based on the same foundation as ICD and ICHI and share the same set of extension codes that enable documentation at a higher level of detail.\"\r\n\r\nOfficial updates to the ICF are available as annual lists of changes.\r\n\r\nThese updates are approved annually at the October meeting of the WHO Family of International Classifications (WHO-FIC) Network.\r\n\r\nTo license ICF, the same rules apply for ICF as for ICD. See [http://icd.who.int/](http://icd.who.int/).\r\n\r\nFor more information, see [https://www.who.int/standards/classifications/international-classification-of-functioning-disability-and-health](https://www.who.int/standards/classifications/international-classification-of-functioning-disability-and-health)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ICFDut"
},
"name" : "International Classification of Functioning, Disability and Health, Dutch Translation",
"description" : "\"The International Classification of Functioning, Disability and Health, known more commonly as ICF, is a classification of health and health-related domains. As the functioning and disability of an individual occurs in a context, ICF also includes a list of environmental factors.\r\n\r\nICF is the WHO framework for measuring health and disability at both individual and population levels.\r\n\r\nICF was officially endorsed by all 191 WHO Member States in the Fifty-fourth World Health Assembly on 22 May 2001(resolution [WHA 54.21](http://apps.who.int/gb/archive/pdf_files/WHA54/ea54r21.pdf) ) as the international standard to describe and measure health and disability.\r\n\r\nICF is based on the same foundation as ICD and ICHI and share the same set of extension codes that enable documentation at a higher level of detail.\"\r\n\r\n\"The Dutch translation of the ICF is published in book form by BSL. The ICF can also be consulted online in the [Classification Browser](https://class.whofic.nl/browser.aspx?scheme=ICF-nl.cla).\r\n\r\nThe ICF team of the WHO-FIC Collaborating Center combines expertise in the field of the ICF for the Dutch language area and currently consists of delegations from the Netherlands Paramedical Institute, the University Medical Center Groningen, Maastricht University, the Big Move Institute, Stichting Scientific Research Road Safety, University of Ghent, Vilans, and Rehabilitation Center de Hoogstraat.\"\r\n\r\nOfficial updates to the ICF are available as annual lists of changes.\r\n\r\nThese updates are approved annually at the October meeting of the WHO Family of International Classifications (WHO-FIC) Network.\r\n\r\nTo license ICF, the same rules apply for ICF as for ICD. See [http://icd.who.int/](http://icd.who.int/).\r\n\r\nFor more information, see [https://www.whofic.nl/familie-van-internationale-classificaties/referentie-classificaties/icf](https://www.whofic.nl/familie-van-internationale-classificaties/referentie-classificaties/icf)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ICPC3"
},
"name" : "International Classification of Primary Care - Third Revision",
"description" : "The International Classification of Primary Care (ICPC) is the most widely used international classification for systematically capturing and organising clinical information in primary care. It is a unifying language for Primary Care, supporting the coherent coding of reason(s) for encounter, symptoms and complaints, diagnoses, health problems, functioning, environmental factors, personal factors related to health and processes of care, all in only one classification."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/IECColourManagement"
},
"name" : "IEC 61966-2-1: Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB",
"description" : "IEC 61966-2-1:1999 is the official specification of sRGB. It provides viewing environment, encoding, and colorimetric details.\r\n\r\nFor more information, please see https://webstore.iec.ch/publication/6168"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ILRSpeakingSkillScale"
},
"name" : "Interagency Language Roundtable Speaking Skill Scale",
"description" : "The following Interagency Language Roundtable (ILR) Skill Level Descriptions (SLDs) describe proficiency as the functional ability to produce spoken language that reflects current usage. The SLDs characterize proficiency ranging from no communicative ability to mastery. They constitute an ordinal scale that includes six ranked base levels from 0 to 5. They illustrate, but do not exhaustively characterize, the proficiency a person may demonstrate at a given level on the scale.\r\n\r\nControl of a base level (Levels 1, 2, 3, 4, and 5) typically implies control of the previous levels' aspects. A higher level of performance in one aspect does not justify a higher general proficiency rating. Level 5 includes the features of all levels. Still, as with all levels, Level 5 is a range and performance will vary.\r\n\r\nThere are plus levels for levels 0 through 4. Plus levels describe proficiency that substantially exceeds one base level and does not fully meet the criteria of the next base level. To merit a plus level, the demonstrated proficiency must match the plus level description and not be merely a strong performance at the base level.\r\n\r\nThe SLDs describe four aspects of language proficiency: functional ability (color coded green), precision of forms and meanings (red), content meaningfulness (black), and contextual appropriateness (blue). Functional ability refers to the communicative acts or tasks that an individual can accomplish. There are no functional abilities specific to the plus levels. Precision of forms and meanings refers to accuracy, range, and complexity. Content meaningfulness refers to the relevance and substantive coverage of topics. Contextual appropriateness refers to register, acceptability, and appropriateness of language for the intended audience.\r\n\r\nThe SLDs are presented in an official prose version as well as a supplementary crosswalk matrix. Each level description begins with a bolded main statement that summarizes the features of that level. Color coded supporting statements follow the main statement and describe the four aspects in detail. The crosswalk matrix shows the structure of the SLDs explicitly across the four skills.\r\n\r\nFor more information, including the source content, please see [https://www.govtilr.org/Skills/Speaking.htm](https://www.govtilr.org/Skills/Speaking.htm)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/IMO"
},
"name" : "Intelligent Medical Objects",
"description" : "IMO is a clinical interface terminology, which helps to map diagnostic, procedure and other terminologies to medical concepts and codes."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ISCN"
},
"name" : "International System for Human Cytogenomic Nomenclature (ISCN)",
"description" : "The International System for Human Cytogenetic Nomenclature (ISCN) was created by the International Standing committee on Human Cytogenetic Nomenclature to represent the outcome of cytogenetic tests. ISCN specifies the nomenclature to describe karyotypes, chromosome abnormalities, in situ hybridization, etc. ISCN provides a list of symbols and abbreviated terms in adjunction with a set of rules, which can be used in the description of chromosomes and chromosome abnormalities, such as p for short arm of chromosome, q for long arm of chromosome, cen for centromere, del for deletion, ish for in situ hybridization, and plus sign (+) for gain, etc.\r\n\r\nA LOINC code is created to represent \"chromosome analysis results in ISCN expression\". In HL7 v2 messages, this LOINC code is used in OBX-3 with a coded result (CWE data type) that will be sent in OBX-5. The value of the coded result is an ISCN expression, and ISCN will be the code system for the coded result."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ISO3166Part1"
},
"name" : "ISO 3166-1 Codes for the representation of names of countries and their subdivisions â Part 1: Country code",
"description" : "ISO 3166-1 establishes codes that represent the current names of countries, dependencies, and other areas of particular geopolitical interest, on the basis of country names obtained from the United Nations."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ISO3166Part2"
},
"name" : "ISO 3166-2 Codes for the representation of names of countries and their subdivisions â Part 2: Country subdivision code",
"description" : "ISO 3166-2 establishes a code that represents the names of the principal administrative divisions, or similar areas, of the countries and entities included in ISO 3166-1."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ISO3166Part3"
},
"name" : "ISO 3166-3 Codes for the representation of names of countries and their subdivisions â Part 3: Code for formerly used names of countries",
"description" : "ISO 3166-3 establishes a code that represents non-current country names, i.e. the country names deleted from ISO 3166 since its first publication in 1974."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/hcp-lan-apm-framework"
},
"name" : "The Health Care Payment Learning and Action Network (HCPLAN) Alternative Payment Model (APM) Framework Categories",
"description" : "\"The Health Care Payment Learning and Action Network (HCPLAN or LAN) [https://hcp-lan.org/](https://hcp-lan.org/) is a public-private partnership established in 2015 by the US Department of Health and Human Services (HHS) to accelerate the transition to value-based payment models in the US healthcare system.\"\r\n\r\n \"The Framework represents payments from public and private payers to provider organizations (including payments between the payment and delivery arms of highly integrated health systems). It is designed to accommodate payments in multiple categories that are made by a single payer, as well as single provider organizations that receive payments in different categoriesâpotentially from the same payer.\"\r\n\r\n \"Since the original APM Framework White Paper was released in January 2016, it has become the foundation for implementing APMs and evaluating progress toward health care payment reform. Payers, providers, and purchasers have all used the APM Framework to better understand the payment reform landscape and to set goals for participation in APMs, and health care stakeholders have used the APM Framework to identify common goals for transforming the nationâs health care system. Overall, the APM Frameworkâs classification system has been adopted by the health care ecosystem.\"\r\n\r\n \"The LAN APM Framework represents a continuum of payment approaches across four Categories.\"\r\n\r\n Initial version of the APM Framework White Paper was published in 2016. The updated version of the White Paper was published in 2017.\r\n\r\n For more information, please see [https://hcp-lan.org/workproducts/apm-refresh-whitepaper-final.pdf](https://hcp-lan.org/workproducts/apm-refresh-whitepaper-final.pdf)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/MEDRT"
},
"name" : "Medication Reference Terminology (MED-RT)",
"description" : "Medication Reference Terminology (MED-RT) is the evolutionary successor to the Veterans Health Administration National Drug File â Reference Terminology (VHA NDF-RT). Both are formal ontology representations of medication terminology, pharmacologic classifications, and asserted authoritative relationships between them.\r\n\r\nThe MED-RT code system includes relationships between MED-RT concepts and concepts in external code systems, as well as relationships between concepts only in the external code systems. The external code systems that MED-RT references include RxNorm, MeSH, and SNOMED CT US Edition.\r\n\r\nMED-RT can be downloaded from https://evs.nci.nih.gov/ftp1/MED-RT/ \r\n\r\nFor more information, please see https://ncit.nci.nih.gov/ncitbrowser/pages/vocabulary.jsf?dictionary=MED-RT"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/MONDO"
},
"name" : "Mondo Disease Ontology",
"description" : "The Mondo Disease Ontology is a semi-automatically constructed ontology that merges in multiple disease resources to yield a coherent merged ontology that contains cross-species disease terminology.\r\n\r\nNumerous sources for disease definitions and data models currently exist, which include HPO, OMIM, SNOMED CT, ICD, PhenoDB, MedDRA, MedGen, ORDO, DO, GARD, etc; however, these sources partially overlap and sometimes conflict, making it difficult to know definitively how they relate to each other. This has resulted in a proliferation of mappings between disease entries in different resources; however mappings are problematic: collectively, they are expensive to create and maintain. Most importantly, the mappings lack completeness, accuracy, and precision; as a result, mapping calls are often inconsistent between resources. The UMLS provides intermediate concepts through which other resources can be mapped, but these mappings suffer from the same challenges: they are not guaranteed to be one-to-one, especially in areas with evolving disease concepts such as rare disease.\r\n\r\nIn order to address the lack of a unified disease terminology that provides precise equivalences between disease concepts, we created Mondo, which provides a logic-based structure for unifying multiple disease resources.\r\n\r\nMondoâs development is coordinated with the Human Phenotype Ontology (HPO), which describes the individual phenotypic features that constitute a disease. Like the HPO, Mondo provides a hierarchical structure which can be used for classification or ârolling upâ diseases to higher level groupings. It provides mappings to other disease resources, but in contrast to other mappings between ontologies, we precisely annotate each mapping using strict semantics, so that we know when two disease names or identifiers are equivalent or one-to-one, in contrast to simply being closely related.\r\n\r\nFor more information, see [https://mondo.monarchinitiative.org/](https://mondo.monarchinitiative.org/)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/MSDRG"
},
"name" : "Medicare Severity Diagnosis Related Groups (MS-DRGs)",
"description" : "Section 1886(d) of the Act specifies that the Secretary shall establish a classification system (referred to as DRGs) for inpatient discharges and adjust payments under the IPPS based on appropriate weighting factors assigned to each DRG. Therefore, under the IPPS, we[CMS] pay for inpatient hospital services on a rate per discharge basis that varies according to the DRG to which a beneficiary's stay is assigned. The formula used to calculate payment for a specific case multiplies an individual hospital's payment rate per case by the weight of the DRG to which the case is assigned. Each DRG weight represents the average resources required to care for cases in that particular DRG, relative to the average resources used to treat cases in all DRGs. Congress recognized that it would be necessary to recalculate the DRG relative weights periodically to account for changes in resource consumption. Accordingly, section 1886(d)(4)(C) of the Act requires that the Secretary adjust the DRG classifications and relative weights at least annually. These adjustments are made to reflect changes in treatment patterns, technology, and any other factors that may change the relative use of hospital resources.\r\n\r\nCurrently, cases are classified into Medicare Severity Diagnosis Related Groups (MS-DRGs) for payment under the IPPS based on the following information reported by the hospital: the principal diagnosis, up to 25 additional diagnoses, and up to 25 procedures performed during the stay. In a small number of MS-DRGs, classification is also based on the age, sex, and discharge status of the patient. Effective October 1, 2015, the diagnosis and procedure information is reported by the hospital using codes from the International Classification of Diseases, Tenth Revision, Clinical Modification (ICD-10-CM) and the International Classification of Diseases, Tenth Revision, Procedure Coding System (ICD-10-PCS).\r\n\r\nContent can be obtained on the CMS hosted page located at https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/AcuteInpatientPPS/MS-DRG-Classifications-and-Software \r\n\r\nThe DRGs are released annually with errata published infrequently. The fiscal year and release version should be noted (e.g., 2021.38.R1).\r\n\r\nRequests for annual MS-DRG classification changes and any MS-DRG related inquiries should be sent to the MSDRGClassificationChange@cms.hhs.gov mailbox.\r\n\r\nFor additional information on the MS-DRG system, including yearly reviews and changes to the MS-DRGs, please view prior Inpatient Prospective Payment System (IPPS) proposed and final rules located in the left navigational area of https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/AcuteInpatientPPS/MS-DRG-Classifications-and-Software"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/MeSH"
},
"name" : "Medical Subject Headings",
"description" : "The Medical Subject Headings (MeSH) thesaurus is a controlled and hierarchically-organized vocabulary produced by the National Library of Medicine. It is used for indexing, cataloging, and searching of biomedical and health-related information. MeSH includes the subject headings appearing in MEDLINE/PubMed, the NLM Catalog, and other NLM databases.\r\n\r\nMeSH can be downloaded from https://www.nlm.nih.gov/databases/download/mesh.html\r\n\r\nMeSH can be browsed here: https://meshb.nlm.nih.gov/search"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPBrandGenericIndicator"
},
"name" : "NCPDP Brand Generic Indicator",
"description" : "Denotes brand or generic drug dispensed."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPCompoundCode"
},
"name" : "NCPDP Compound Code",
"description" : "Code indicating whether or not the prescription is a compound."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPDispensedAsWrittenOrProductSelectionCode"
},
"name" : "NCPDP Dispense As Written (DAW)/Product Selection Code",
"description" : "Code indicating whether or not the prescriber's instructions regarding generic substitution were followed."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPPharmacyType"
},
"name" : "NCPDP Pharmacy Type",
"description" : "Type of pharmacy."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPPrescriptionOriginCode"
},
"name" : "NCPDP Prescription Origin Code",
"description" : "Code indicating the origin of the prescription. Indicates whether the prescription was transmitted as an electronic prescription, by phone, by fax, or as a written paper copy."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPProviderIdentificationNumber"
},
"name" : "NCPDP Provider Identification Number",
"description" : "A NCPDP assigned number that provides pharmacies with a unique, 7-digit national identifying number that assists pharmacies in their interactions with federal agencies and third party providers. The NCPDP Provider Identification Number was formerly known as the NABP (National Board of Pharmacy) number. NCPDP also enumerates licensed dispensing sites in the United States as part of its Alternate Site Enumeration Program Numbering System (ASEP). The purpose of this system is to enable a site to identify itself to all third party processors by one standard number, in order to adjudicate claims and receive reimbursement from prescription card programs."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NCPDPRejectCode"
},
"name" : "NCPDP Reject Code",
"description" : "Code indicating the error encountered. Contains exception definitions for use when transaction processing cannot be completed."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NDFRT"
},
"name" : "National Drug File Reference Terminology (NDF-RT)",
"description" : "NDF-RT is a concept-oriented terminology, a collection of concepts, each of which represents a single, unique meaning. Every concept has one fully-specified name and an arbitrary number of other names, all of which are intended to mean the same thing and are therefore synonymous terms. Synonymous terms from external vocabulary sources may have associated unique identifiers. Publication of NDF-RT has ended. The Medication Reference Terminology (MED-RT) is the evolutionary successor to the NDF-RT."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/NPU"
},
"name" : "Nomenclature for Properties and Units (NPU)",
"description" : "The NPU terminology is a coding system and terminology for identification and communication of examinations for ordering and reporting results between clinical laboratories and laboratory information systems, hospital patient records, general practitioners (GP) and local and national data repositories."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/OMOP"
},
"name" : "OHDSI Standardized Vocabularies",
"description" : "Standardized Vocabularies are an integral part of the OMOP CDM. The Standardized Vocabularies contain all of the code sets, terminologies, vocabularies, nomenclatures, lexicons, thesauri, ontologies, taxonomies, classifications, abstractions, and other such data that are needed for:\r\n\r\n* Generation of the transformed (i.e., standardized) data from the raw source dataset into the OMOP CDM,\r\n\r\n* Searching, querying and extraction of the transformed data, and browsing and navigating the hierarchies of classes and abstractions inherent in the transformed data, and\r\n\r\n* Interpreting the meanings of the data.\r\n\r\nThis asset is available for free to anyone and can be [downloaded](https://athena.ohdsi.org/vocabulary/list) from the Atena download page in a delimited file format.\r\n\r\nTo manage the change of content, but to allow users to use and refer to a defined set of vocabularies, the whole resource is issued in releases. Major changes to the OMOP Vocabulary is released twice yearly in February and August. Instead of a major / minor version scheme, the releases of the Standardized Vocabularies component of the OMOP Vocabulary are tagged with the release date. Version label is based on the version of the CDM its aligned-to, plus a suffix appended incremented based on release date, for example: âv5.0 31-MAY-23.â At this time prior versions of the OMOP Vocabulary are not publicly available. Each release is accompanied by a [standard release note](https://github.com/OHDSI/Vocabulary-v5.0/releases), containing information about:\r\n\r\n* Domain changes\r\n\r\n* Newly added concepts grouped by vocabulary_id and domain\r\n\r\n* Standard concept changes\r\n\r\n* Newly added concepts and their standard concept status\r\n\r\n* Changes of concept mapping status grouped by target domain\r\n\r\nAdditional details about the OMOP Vocabulary release notes can be found [here](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Releases)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/OpenEligibilityTaxonomy"
},
"name" : "Open Eligibility Taxonomy",
"description" : "\"The Open Eligibility Project is a collaborative for a series of standards for the human services sector. The Open Eligibility taxonomy is a simple way to categorize human services and human situations. With these common categories, we, as service providers, navigators, and people in need, can find human services quickly and easily.\"\r\n\r\n\"The Open Eligibility taxonomy consists of two important concepts: Human Services and Human Situations.\r\n\r\nHuman Services are services offered by government or charitable organizations, and include things such as housing, food pantries or counseling services.\r\n\r\nHuman Situations are ways of describing attributes of a person that could help them find programs they are looking for, including examples like: veterans, physical disability or seniors.\"\r\n\r\nFor more information, see [https://support.findhelp.com/hc/en-us/articles/4404055283227-The-Open-Eligibility-Project](https://support.findhelp.com/hc/en-us/articles/4404055283227-The-Open-Eligibility-Project)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXMethodofPayment"
},
"name" : "PMIX Method of Payment",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nMethod of Payment: The PMIX equivalent to the DSP16 field of the ASAP format which identifies the primary method of payment for the prescription, for use in PDMP (Prescription Drug Monitoring Program) data exchanges."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXOpioidTreatmentCode"
},
"name" : "PMIX Opioid Treatment Code",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nOpioid Treatment Code: The PMIX equivalent to the DSP24 field of the ASAP format which identifies whether or not the prescription is for the purpose of treating Opioid Use Disorder, and if so, the type of treatment. For use in PDMP (Prescription Drug Monitoring Program) data exchanges."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXPatientAlertCatCode"
},
"name" : "PMIX Patient Alert Category Code",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nPatient Alert Category Code: In the event that the PDMP (Prescription Drug Monitoring Program) utilizes an âalertâ functionality â a functionality that alerts an end user to some known or detected activity or condition regarding the requested patient â the alert category code indicates what type of alert was detected and is being sent by the PDMP."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXSpeciesTypeCode"
},
"name" : "PMIX Species Type Code",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nSpecies Type Code: The PMIX equivalent to the PAT20 field of the ASAP format which identifies whether the patient is a human patient or a veterinary patient, for use in PDMP (Prescription Drug Monitoring Program) data exchanges."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXStatusCode"
},
"name" : "PMIX Status Code",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nStatus Code: A code that indicates the status of the request to the PDMP (Prescription Drug Monitoring Program)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PMIXTransmissionFormRxOriginCodeType"
},
"name" : "PMIX Transmission Form Of Rx Origin Code Type",
"description" : "This code system is part of the PMIX National Architecture. The Prescription Monitoring Information eXchange (PMIX) Standards Organization is the sole body responsible for developing, updating and maintaining all aspects of the PMIX National Architecture and any related standards, documentation and/or guidance documents. The PMIX Standards Organization is made up of State Prescription Drug Monitoring Programs, Prescription Drug Monitoring Program Vendors, Third-Party Intermediaries and Federal Agencies. The appropriate contacts for PMIX are the Chair and Vice Chair of the PMIX Executive Committee.\r\n\r\nChair: [Chad Garner](mailto:chad.garner@pharmacy.ohio.gov)\r\n\r\nVice Chair: [Chelsea Townsend](mailto:townseca@dhec.sc.gov)\r\n\r\nTransmission Form Of Rx Origin Code Type: The PMIX equivalent to the DSP12 field of the ASAP format which identifies by which method the pharmacy received the prescription, for use in PDMP (Prescription Drug Monitoring Program) data exchanges."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/PharmVar"
},
"name" : "Pharmacogene Variation",
"description" : "\"The major focus of the Pharmacogene Consortium (PharmVar) is to serve as a repository for allelic variation, providing an official and unified allele designation system for the Pharmacogenetics (PGx) community and facilitating the translation of genotype into phenotype and clinical implementation of PGx. While the majority of pharmacogenes in PharmVar utilize the star nomenclature to describe variation, the provision of single nucleotide variants (SNVs), rather than haplotype, is preferred for some genes. Thus, PharmVar has two different page formats, A) using star nomenclature and B) using rs ID# as allele (referred to as ârs-formatâ).\r\n\r\nPharmVar designates human pharmacogene variation and houses allelic variants in the PharmVar database.\r\n\r\n* All submissions to PharmVar must use the submission form available on [www.PharmVar.org](https://www.pharmvar.org/) and be submitted to [submissions@PharmVar.org](mailto:submissions@PharmVar.org). Only complete submission requests will be accepted and processed.\r\n\r\n* PharmVar Gene Expert Panels will review each submission and make a recommendation to the PharmVar Steering Committee.\r\n\r\n* In this âAllele Designation Criteria and Evidence levelâ document, we collectively refer to deviations from the RefSeq as âsequence variationsâ or \"SNVs\", including single nucleotide polymorphisms (SNPs) and small nucleotide insertions and deletions (indels) up to 50 bp. Copy number variants (i.e. entire or partial gene deletions and duplications), hybrid genes (e.g. CYP2D6/2D7 hybrids) and duplications containing non-identical gene copies (e.g. CYP2D6\\*36+\\*10) are referred to as CNVs or structural variants.\r\n\r\n* PharmVar applies the following criteria for allele designation. In rare cases, exceptions may be made to accommodate established star allele definitions to minimize impact on research, clinical labs and/or PGx implementation.\"\r\n\r\nPharmVar is released monthly (or more frequently) and uses a numbered database version format for each release.\r\n\r\nNote on updates to variants: The variants defined in association with a given PharmVar ID are immutable. When it is necessary to update the variant definitions for an associated concept, the existing allele and PharmVar ID are marked as \"retired\" and a new PharmVar ID is issued with the updated variant definitions.\r\n\r\nIn the context of the representation of PharmVar in HL7 standards:\r\n\r\n* The concept identifier is the PharmVar ID\r\n\r\n* The concept display name is the Allele Name\r\n\r\n* There are several concept properties associated with PharmVar concepts (Legacy Label, Variants, etc.)\r\n\r\n* The code system is represented with an is-a hierarchy"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/RARC"
},
"name" : "X12 Remittance Advice Remark Codes",
"description" : "X12, chartered by the American National Standards Institute for more than 40 years, develops and maintains EDI standards and XML schemas which drive business processes globally. X12's diverse membership includes technologists and business process experts in health care, insurance, transportation, finance, government, supply chain and other industries.\r\n\r\nRemittance Advice Remark Codes (RARCs) are used to provide additional explanation for an adjustment already described by a Claim Adjustment Reason Code (CARC) or to convey information about remittance processing. Each RARC identifies a specific message as shown in the Remittance Advice Remark Code List. There are two types of RARCs, supplemental and informational. The majority of the RARCs are supplemental; these are generally referred to as RARCs without further distinction. Supplemental RARCs provide additional explanation for an adjustment already described by a CARC. The second type of RARC is informational; these RARCs are all prefaced with Alert: and are often referred to as Alerts. Alerts are used to convey information about remittance processing and are never related to a specific adjustment or CARC."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/RadLex"
},
"name" : "RadLex radiology lexicon",
"description" : "RadLex is a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.\r\n\r\nRadLex Playbook is a project of the Radiological Society of North America (RSNA), and constitutes a portion of the RadLex ontology. Playbook aims to provide a standard system for naming radiology procedures, based on the elements which define an imaging exam such as modality and body part. By providing standard names and codes for radiologic studies, Playbook is intended to facilitate a variety of operational and quality improvement efforts, including workflow optimization, chargemaster management, radiation dose tracking, enterprise integration and image exchange.\r\n\r\nAs of RadLex Playbook version 2.5, a four-year project to harmonize RadLex Playbook with the radiology portion of the LOINC standard has been concluded, leading to the LOINC-RSNA Radiology Playbook which is jointly managed by the Regenstrief Institute (publisher of LOINC) and RSNA. This harmonized Playbook defines a new information model for describing imaging procedures, and identifies correspondences between RadLex Playbook codes and LOINC codes. (See https://loinc.org/download/loinc-users-guide and http://pubs.rsna.org/doi/pdf/10.1148/rg.2017160188 for details.) Note that RadLex Playbook codes start with \"RPID\" followed by a numerical value. LOINC codes consist of a numerical code, followed by a hyphen and a single additional digit (called the check digit). Note that in the future, new codes will be created in the LOINC format only, not the RPID format. New adopters are encouraged to use LOINC-format codes.\r\n\r\nLOINC-format codes may be accessed at http://search.loinc.org. New code requests may be submitted to the joint Regenstrief-RSNA governance committee at https://loinc.org/submissions/. \r\n\r\nFrom the RSNA website:\r\n\r\n\"We (RSNA) recognize the benefits that come from radiologists using common language to communicate diagnostic results. For this reason, RSNA produced RadLex®, a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.\r\n\r\nRadLex provides the foundation for vital data resources used in radiology:\r\n\r\n * The LOINC/RSNA Radiology Playbook (http://playbook.radlex.org/playbook/SearchRadlexAction) \r\n * RadElement Common Data Elements (http://www.radelement.org/) \r\n * RadReport Radiology Reporting Templates (http://radreport.org/) \r\n\r\nThe development of RadLex has been supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) and the cancer Biomedical Informatics Grid (caBIG) project.;\""
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/SO"
},
"name" : "Sequence Ontology",
"description" : "\"The Sequence Ontology is a set of terms and relationships used to describe the features and attributes of biological sequence. SO includes different kinds of features which can be located on the sequence. Biological features are those which are defined by their disposition to be involved in a biological process.\"\r\n\r\n\"The Sequence Ontologies are provided as a resource to the biological community. They have the following obvious uses:\r\n\r\n* To provide for a structured controlled vocabulary for the description of primary annotations of nucleic acid sequence, e.g. the annotations shared by a DAS server ([BioDAS](http://www.biodas.org/documents/das2/das2_protocol.html), [Biosapiens DAS](http://www.biosapiens.info/page.php?page=das_portal)), or annotations encoded by [GFF3](http://www.sequenceontology.org/gff3.shtml).\"\r\n\r\n* To provide for a structured representation of these annotations within databases. Were genes within model organism databases to be annotated with these terms then it would be possible to query all these databases for, for example, all genes whose transcripts are edited, or trans-spliced, or are bound by a particular protein. One such genomic database is [Chado](http://www.gmod.org/wiki/Chado).\r\n\r\n* To provide a structured controlled vocabulary for the description of mutations at both the sequence and more gross level in the context of genomic databases.\"\r\n\r\n\"The Sequence Ontology is part of [OBO](http://www.obofoundry.org/). It has close links to other ontology projects such as the [RNAO consortium](http://roc.bgsu.edu/), and the [Biosapiens polypeptide features](http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=BS).\"\r\n\r\nThe content can be browsed [here](http://www.sequenceontology.org/browser/obob.cgi)\r\n\r\nThe content can be downloaded [here](https://github.com/The-Sequence-Ontology/SO-Ontologies)\r\n\r\nFor information on contributing, please see [here](https://github.com/The-Sequence-Ontology/SO-Ontologies#contributing)\r\n\r\nTo request a term or register feedback, see [here](https://github.com/The-Sequence-Ontology/SO-Ontologies/issues)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/SOPT"
},
"name" : "Source of Payment Typology",
"description" : "The Source of Payment Typology is a standardized Payer Type classification system. It is a mechanism for consistent reporting of payer data to state health data organizations and supports data comparisons by payer type across states, various provider types, and to national benchmarks. Developed by the Public Health Data Standards Consortium (PHDSC) Payer Typology Subcommittee, the typology includes broad hierarchial payer type categories with more specific subcategories. \r\n\r\nThe audience for Source of Payment Typology includes researchers, public health advocates, and healthcare analysts."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/TNM"
},
"name" : "TNM Staging System",
"description" : "The TNM Staging System was developed and is maintained by the AJCC and the Union for International Cancer Control (UICC). It is the most commonly used staging system by medical professionals around the world. The TNM classification system was developed as a tool for doctors to stage different types of cancer based on certain, standardized criteria. The TNM Staging System is based on the extent of the tumor (T), the extent of spread to the lymph nodes (N), and the presence of metastasis (M).\r\n\r\nHTA Note: Most content of TNM (V6) is in the SNOMED international release but not content from the most recent (V9). In Europe many countries use TNM codes, taken from the book and referenced using an OID."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/TangramMedicalTerminology"
},
"name" : "OMAHA Tangram Medical Terminology",
"description" : "OMAHA Tangram Medical Terminology is an ontology-based medical terminological resource developed by Chinese language. It helps to standardize the expression of Chinese medical terms, and improve the semantic interoperability between different systems. The terminology can be used in electronic health records, decision support systems and digital health researches, providing the functions of mapping, data capture, data mining, data registries, statistical analysis and reasoning etc.\r\n\r\nTangram Medical Terminology is released quarterly using the file name format as Tangram_Medical_Terminology _YYYYMMDD (Example: Tangram _Medical_Terminology _20200120). For more information, please visit http://wiki.omaha.org.cn/pages/viewpage.action?pageId=31425763 \r\n\r\nFor more information, see https://term.omaha.org.cn/."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/UNII"
},
"name" : "Unique Ingredient Identifier (UNII)",
"description" : "A UNII is a non-proprietary, free, unique, unambiguous, nonsemantic, alphanumeric identifier based on a substance's molecular structure and/or descriptive information. UNII identifiers are generated based on scientific identity characteristics using ISO 11238 data elements. UNII availability does not imply any regulatory review or approval. Synonyms and mappings are based on the best public information available at the time of publication."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/W3CDID"
},
"name" : "W3C Decentralized Identifier (DID)",
"description" : "\"[Decentralized identifiers](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the [DID](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers). In contrast to typical, federated identifiers, [DIDs](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a [DID](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers), the design enables the controller of a [DID](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) to prove control over it without requiring permission from any other party. [DIDs](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) are [URIs](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-uri) that associate a [DID subject](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-subjects) with a [DID document](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-documents) allowing trustable interactions associated with that subject.\r\n\r\nEach [DID document](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-documents) can express cryptographic material, [verification methods](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-verification-method), or [services](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-service), which provide a set of mechanisms enabling a [DID controller](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-controllers) to prove control of the [DID](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers). [Services](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-service) enable trusted interactions associated with the [DID subject](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-subjects). A [DID](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) might provide the means to return the [DID subject](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-subjects) itself, if the [DID subject](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-did-subjects) is an information resource such as a data model.\"\r\n\r\nFor more information, see [https://www.w3.org/TR/did-core/](https://www.w3.org/TR/did-core/)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/X12AmbulanceTransportReasonCodes"
},
"name" : "X12 Ambulance Transport Reason Codes",
"description" : "\"X12, chartered by the American National Standards Institute for more than 40 years, develops and maintains EDI standards and XML schemas which drive business processes globally. X12's diverse membership includes technologists and business process experts in health care, insurance, transportation, finance, government, supply chain and other industries.\"\n\nThe X12 Ambulance Transport Reason Codes indicate the reason for ambulance transport. These codes are listed within an X12 implementation guide (TR3) and maintained by X12.\n\nA list of codes and associated descriptions established, maintained, and published as part of an X12 Standard."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/X12ClaimAdjustmentReasonCodes"
},
"name" : "X12 Claim Adjustment Reason Codes",
"description" : "\"X12, chartered by the American National Standards Institute for more than 40 years, develops and maintains EDI standards and XML schemas which drive business processes globally. X12's diverse membership includes technologists and business process experts in health care, insurance, transportation, finance, government, supply chain and other industries.\"\r\n\r\nThe X12 Claim Adjustment Reason Codes describe why a claim or service line was paid differently than it was billed. These codes are listed within an X12 implementation guide (TR3) and maintained by X12.\r\n\r\nExternal code lists maintained by X12 and external code lists maintained by others and distributed by WPC on behalf of the maintainer can be found here: [here](https://x12.org/codes)\r\n\r\nClick on the name of any external code list to access more information about the code list, view the codes, or submit a maintenance request. These external code lists were previously published on either [www.wpc-edi.com/reference](http://www.wpc-edi.com/reference) or [www.x12.org/codes](https://x12.org/codes)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/X12ServiceTypeCodes"
},
"name" : "X12 Service Type Codes",
"description" : "\"X12, chartered by the American National Standards Institute for more than 40 years, develops and maintains EDI standards and XML schemas which drive business processes globally. X12's diverse membership includes technologists and business process experts in health care, insurance, transportation, finance, government, supply chain and other industries.\"\r\n\r\nThe X12 Service Type Codes identify business groupings for health care services or benefits. These codes are listed within an X12 implementation guide (TR3) and maintained by X12.\r\n\r\nExternal code lists maintained by X12 and external code lists maintained by others and distributed by WPC on behalf of the maintainer can be found here: [https://x12.org/codes](https://x12.org/codes)\r\n\r\nClick on the name of any external code list to access more information about the code list, view the codes, or submit a maintenance request. These external code lists were previously published on either [http://www.wpc-edi.com/reference](http://www.wpc-edi.com/reference) or [http://www.x12.org/codes](http://www.x12.org/codes).\r\n\r\nIf you have questions about these lists, submit them on the [X12 Feedback form](https://x12.org/resources/feedback).\r\n\r\n\"All X12 products are subject to this IP policy, including published and draft works.\r\n\r\nX12 is the only organization authorized to grant permission for use of X12 products. Users of all X12 products should make sure that they understand the permissible uses, as well as the limitations on such usage, as outlined below.\"\r\n\r\nAdditional IP information can be found here: [https://x12.org/products/ip-use](https://x12.org/products/ip-use)\r\n\r\n\"Send an email to [ip@x12.org](mailto:ip@x12.org) to request permission to reproduce X12 IP. Include your name, organization, title, address, city, state, zip, email, a detailed description of the Submitted Artifact, including the underlying or cited X12 Product, and a detailed description of the intended audience and planned distribution method for the Artifact.\"\r\n\r\nAdditional information on X12 licensing program can be found here: [https://x12.org/products/licensing-program](https://x12.org/products/licensing-program)\r\n\r\nTo purchase code list subscriptions call (425) 562-2245 or email [admin@wpc-edi.com](mailto:admin@wpc-edi.com)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ClinVarV"
},
"name" : "ClinVar Variant ID",
"description" : "ClinVar is a freely accessible, public archive of reports of the relationships among human variations and phenotypes, with supporting evidence. ClinVar thus facilitates access to and communication about the relationships asserted between human variation and observed health status, and the history of that interpretation. ClinVar processes submissions reporting variants found in patient samples, assertions made regarding their clinical significance, information about the submitter, and other supporting data. The alleles described in submissions are mapped to reference sequences, and reported according to the HGVS standard. ClinVar then presents the data for interactive users as well as those wishing to use ClinVar in daily workflows and other local applications. ClinVar works in collaboration with interested organizations to meet the needs of the medical genetics community as efficiently and effectively as possible. Read more about using ClinVar.\r\n\r\nClinVar supports submissions of differing levels of complexity. The submission may be as simple as a representation of an allele and its interpretation (sometimes termed a variant-level submission), or as detailed as providing multiple types of structured observational (case-level) or experimental evidence about the effect of the variation on phenotype. A major goal is to support computational (re)evaluation, both of genotypes and assertions, and to enable the ongoing evolution and development of knowledge regarding variations and associated phenotypes. ClinVar is an active partner of the ClinGen project, providing data for evaluation and archiving the results of interpretation by recognized expert panels and providers of practice guidelines (see https://www.ncbi.nlm.nih.gov/clinvar/docs/review_guidelines/). ClinVar archives and versions submissions which means that when submitters update their records, the previous version is retained for review. Read more about submitting data to ClinVar at https://www.ncbi.nlm.nih.gov/clinvar/docs/submit. \r\n\r\nThe level of confidence in the accuracy of variation calls and assertions of clinical significance depends in large part on the supporting evidence, so this information, when available, is collected and visible to users. Because the availability of supporting evidence may vary, particularly in regard to retrospective data aggregated from published literature, the archive accepts submissions from multiple groups, and aggregates related information, to reflect transparently both consensus and conflicting assertions of clinical significance. A review status is also assigned to any assertion, to support communication about the trustworthiness of any assertion. Domain experts are encouraged to apply for recognition as an expert panel (more info at https://www.ncbi.nlm.nih.gov/clinvar/docs/review_guidelines/). \r\n\r\nAccessions, with the format SCV000000000.0, are assigned to each submitted record. If there are multiple submitted records about the same variation/condition pair, they are aggregated within ClinVar's data flow and reported as a reference accession with the format RCV000000000.0. Because of this model, one variant will be included in multiple RCV accessions whenever different conditions are reported for that variant. Submitted records for the same variation are also aggregated and reported as an accession with the format VCV000000000.0. This aggregation lets a user review all submitted data for a variant, regardless of the condition for which it was interpreted.\r\n\r\nClinVar archives submitted information, and adds identifiers and other data that may be available about a variant or condition from other public resources. However ClinVar neither curates content nor modifies interpretations independent of an explicit submission. If you have data that differs from what is currently represented in ClinVar, we encourage you to submit your data and the evidence supporting your interpretation. There is a submission wizard to guide you through that process. See https://www.ncbi.nlm.nih.gov/variation/clinvar_single_wizard/. \r\n\r\nIf you are submitting variants that were interpreted as part of work funded by the NIH, please consult your program officer about expectations for submissions to ClinVar."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/cmshcc"
},
"name" : "CMS Hierarchical Condition Categories",
"description" : "The CMS-HCC model uses more than 9,000 ICD-10-CM codes, which are mapped to condition categories that predict costs well. The condition categories are based on diagnoses clinically related to one another and with similar predicted cost implications. Hierarchies are imposed on the condition categories to capture the most costly diagnoses. Hierarchy logic is imposed on certain condition categories to account for different hierarchical costs, thus, the term Hierarchical Condition Category, or HCC.\r\n\r\nFor more information, see https://www.cms.gov/Medicare/Health-Plans/MedicareAdvtgSpecRateStats/Risk-Adjustors.\r\n\r\nThe CMS HCCs are in the public domain and are free to use without restriction."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/ca-hc-din"
},
"name" : "Health Canada Drug Id Number",
"description" : "A Drug Identification Number (DIN) is a computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. It uniquely identifies all drug products sold in a dosage form in Canada and is located on the label of prescription and over-the-counter drug products that have been evaluated and authorized for sale in Canada. A DIN uniquely identifies the following product characteristics:\r\n\r\n * manufacturer\r\n * product name\r\n * active ingredient(s)\r\n * strength(s) of active ingredient(s)\r\n * pharmaceutical form, and\r\n * route of administration.\r\n\r\nNote: The number has a leading zero.\r\n\r\nFurther information about this Code System can be found at https://www.canada.ca/en/health-canada/services/drugs-health-products/drug-products/applications-submissions/guidance-documents/regulatory-requirements-drug-identification-numbers/document.html"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/hcpcs-Level-II"
},
"name" : "Healthcare Common Procedure Coding System (HCPCS) level II alphanumeric codes",
"description" : "The Level II HCPCS codes, which are established by CMS's Alpha-Numeric Editorial Panel, primarily represent items and supplies and non-physician services not covered by the American Medical Association's Current Procedural Terminology-4 (CPT-4) codes; Medicare, Medicaid, and private health insurers use HCPCS procedure and modifier codes for claims processing. Level II alphanumeric procedure and modifier codes comprise the A to V range."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/presentOnAdmission"
},
"name" : "CMS Present on Admission (POA) Indicator",
"description" : "This code system consists of Present on Admission (POA) indicators which are assigned to the principal and secondary diagnoses (as defined in Section II of the Official Guidelines for Coding and Reporting) and the external cause of injury codes to indicate the presence or absence of the diagnosis at the time of inpatient admission."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "CodeSystem"
}
],
"reference" : {
"reference" : "CodeSystem/v3-hgnc"
},
"name" : "HUGO Gene Nomenclature Committee Genes",
"description" : "\"The HGNC is responsible for approving unique symbols and names for human loci, including protein coding genes, ncRNA genes and pseudogenes, to allow unambiguous scientific communication.\"\r\n\r\nThe HGNC gene table carries gene IDs, gene symbols and full gene names. Guidance from HGNC confirms that gene symbols are not unique across species and have been known to change in some instances. Thus the commonly used gene symbols should be encoded in FHIR as \"displays\" with the corresponding IDs (beginning with \"HGNC:\") as the \"codes\".\r\n\r\n\"For each known human gene we approve a gene name and symbol (short-form abbreviation). All approved symbols are stored in the HGNC database,[www.genenames.org](https://www.genenames.org/tools/search), a curated online repository of HGNC-approved gene nomenclature, gene groups and associated resources including links to genomic, proteomic and phenotypic information. Each symbol is unique and we ensure that each gene is only given one approved gene symbol. It is necessary to provide a unique symbol for each gene so that we and others can talk about them, and this also facilitates electronic data retrieval from publications and databases.\"\r\n\r\nHGNC also provides an index on gene families/groups. GeneGroup IDs do not begin with \"HGNC:\", so care must be made to ensure alignment of concepts when viewing an HGNC ID from an older system that may be referring to the GeneID and not a gene group. For example, 588 refers to the HLA gene family, but HGNC:588 identifies the ATG12 gene. To provide clarity for systems that do not distinguish codes from genes and gene families, use \"http://www.genenames.org\" for genes and \"http://www.genenames.org/genegroup\" for gene families as code system URIs.\r\n\r\nFor more information on HGNC Gene Groups, see [https://terminology.hl7.org/CodeSystem-HGNCGeneGroup.html](https://terminology.hl7.org/CodeSystem-HGNCGeneGroup.html).\r\n\r\nHistorically, HGNC gene symbols were used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model Implementation Guide, HGNC gene symbols were used as the observation values for gene identifiers. For example, OBX 1 CWE 48018-6^Gene identifier^ BRCA1^HGNC. Please note that gene symbols may be present in legacy systems, but GeneID should be used to exchange HGNC gene information in current implementations.\r\n\r\nHGNC is a free database for the public.\r\n\r\nVersioning Information: The version of the HGNC database is reported using the last updated date. The last updated date is posted on the main HGNC Search screen in the format like \"2024-07-25\".\r\n\r\nCurrent, monthly and quarterly HGNC dataset files are published.\r\n\r\nPlease see https://www.genenames.org/ for more info."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/ADAAreaOralCavitySystem"
},
"name" : "American Dental Association Area of Oral Cavity System",
"description" : "The Area of Oral Cavity System is accepted and approved by the ADA and is the most commonly used system used by dental professionals in America.\r\n\r\nArea of the oral cavity is designated by a two-digit code.\r\n\r\nThe Area of Oral Cavity System can be found in the ADA Comprehensive ADA Dental Claim Form Completion Instructions (see https://www.ada.org/-/media/project/ada-organization/ada/ada-org/files/publications/cdt/v2019adadentalclaimcompletioninstructions_v3_2022feb.pdf). For more information see here: https://www.ada.org/publications/cdt/ada-dental-claim-form. \r\n\r\nA Statement of Understanding (SOU) between ADA and HL7 exists here: http://www.hl7.org/documentcenter/public/mou/ADA%20HL7%20SOU%202021_signed.pdf"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/ADAUniversalToothDesignationSystem"
},
"name" : "ADA Universal Tooth Designation System",
"description" : "The American Dental Association (ADA) accepted the Universal/National Tooth Designation System and the ISO/ANSI/ADA Specification No. 3950 for Designation System for Teeth and Areas of the Oral Cavity as the human tooth and oral cavity enumeration schemas in 1994.\r\n\r\nThe universal tooth designation or numbering system is accepted and approved by the ADA and is the most commonly used system used by dental professionals in America.\r\n\r\nTeeth are numbered 1-32, starting with the third molar (1) on the right side of the upper arch, following around the arch to the third molar (16) on the left side, and descending to the lower third molar (17) on the left side, and following that arch to the terminus of the lower jaw, the lower right third molar (32).\r\n\r\nSupernumerary teeth are identified by the numbers 51 through 82, beginning with the area of the upper right third molar, following around the upper arch and continuing on the lower arch to the area of the lower right third molar (e.g., supernumerary #51 is adjacent to the upper right molar #1; supernumerary #82 is adjacent to the lower right third molar #32).\r\n\r\nThe Universal Numbering System can be found in the ADA Dental Claim Form. For more information see here: https://www.ada.org/publications/cdt/ada-dental-claim-form. \r\n\r\nA Statement of Understanding (SOU) between ADA and HL7 exists here: http://www.hl7.org/documentcenter/public/mou/ADA%20HL7%20SOU%202021_signed.pdf"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCConditionCodes"
},
"name" : "AHA NUBC Condition Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 18-28 Condition Codes\r\n\r\nThese codes are used to convey the applicable Condition Codes and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nNational Uniform Billing Committee Data Element Specifications Change Request Guidelines\r\n\r\n\"The National Uniform Billing Committee (NUBC) holds meetings and conference calls throughout the year and change requests to the UB-04 Manual or UB-04 Data Set may be submitted at any time. To be considered at the next scheduled meeting, requests for changes must be received by the NUBC Secretary at least 45 days in advance. Approved changes are usually effective as of July 1 or about 90 days after approval, as appropriate.\"\r\n\r\nFor more information and to submit a change request, please see [here](https://www.nubc.org/form/change-request-guidelines-form-n)\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCPatientDischargeStatus"
},
"name" : "AHA NUBC Patient Discharge Status Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 17 - Patient Discharge Status\r\n\r\nThese codes are used to convey the patient discharge status and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCPointOfOriginNewborn"
},
"name" : "AHA NUBC Point of Origin for Newborn",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 15 - Point of Origin for Admission or Visit for Newborn\r\n\r\nThese codes are used to convey the patient point of origin for an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCPointOfOriginNonnewborn"
},
"name" : "AHA NUBC Point of Origin for Non-newborn",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 15 - Point of Origin for Admission or Visit for Non-newborn\r\n\r\nThese codes are used to convey the patient point of origin for an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCPriorityTypeOfAdmitOrVisit"
},
"name" : "AHA NUBC Priority (Type) of Admission or Visit",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 14 - Priority (Type) of Admission or Visit\r\n\r\nThese codes are used to convey the priority of an admission or visit and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCRevenueCodes"
},
"name" : "AHA NUBC Revenue Codes",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 42 - Revenue Codes\r\n\r\nThese codes are used to convey the revenue code and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCTypeOfBill"
},
"name" : "AHA NUBC Type Of Bill Codes",
"description" : "The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\r\n\r\nThis code system consists of the following:\r\n\r\n \\* FL 04 - Type of Bill Facility Codes\r\n\r\n \\* FL 04 - Type of Bill Frequency Codes\r\n\r\nA code indicating the specific Type of Bill (TOB), e.g., hospital inpatient, outpatient, replacements, voids, etc. The first digit is a leading zero*. The fourth digit defines the frequency of the bill for the institutional and electronic professional claim.\r\n\r\nNote that with the advent of UB-04, the matrix methodology of constructing the first component of TOB codes according to digit position was abandoned in favor of specifying valid discrete codes. As a result, the first three digits in TOB have no underlying meaning.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nThe UB-04 Manual has a 12-month subscription period from June 30 through July 1."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/AHANUBCValueCodesAndAmounts"
},
"name" : "AHA NUBC Value Codes and Amounts",
"description" : "\"The UB-04 Data File contains the complete set of NUBC codes. Every code in the range of possible codes is accounted for sequentially. There are no gaps because all used and unused codes are identified.\"\r\n\r\nThis code system consists of the following:\r\n\r\n\\* FL 39-41 Value Codes and Amounts\r\n\r\nThese codes are used to convey the applicable Value Codes and Amounts and are the property of the American Hospital Association.\r\n\r\nTo obtain the underlying code systems, please see information [here](https://www.nubc.org/subscription-information)\r\n\r\nStatement of Understanding between AHA and HL7 can be found [here](http://www.hl7.org/documentcenter/public/mou/AHA%20HL7%20SOU%202020%20AHA%20Fully%20Executed.pdf). In particular see sections 4.1d and 4.2.\r\n\r\n\"The UB-04 Manual has a 12-month subscription period from June 30 through July 1.\"\r\n\r\nNational Uniform Billing Committee Data Element Specifications Change Request Guidelines\r\n\r\n\"The National Uniform Billing Committee (NUBC) holds meetings and conference calls throughout the year and change requests to the UB-04 Manual or UB-04 Data Set may be submitted at any time. To be considered at the next scheduled meeting, requests for changes must be received by the NUBC Secretary at least 45 days in advance. Approved changes are usually effective as of July 1 or about 90 days after approval, as appropriate.\"\r\n\r\nFor more information and to submit a change request, please see [here](https://www.nubc.org/form/change-request-guidelines-form-n)\r\n\r\nFor frequently asked questions, see here [here](https://www.nubc.org/nubc-faqs)"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/apdrg"
},
"name" : "All Patient Diagnosis Related Groups (AP DRGs)",
"description" : "In 1987, the state of New York passed legislation instituting a DRG-based prospective payment system for all non-Medicare patients. The legislation included a requirement that the New York State Department of Health (NYDH) evaluate the applicability of the DRGs to a non-Medicare population. In particular, the legislation required that the DRGs be evaluated with respect to neonates and patients with Human Immunodeficiency Virus (HIV) infections. NYDH entered into an agreement with 3M HIS to assist with the evaluation of the need for DRG modifications as well as to make the necessary changes in the DRG definitions and software. The DRG definitions developed by NYDH and 3M HIS are referred to as the All Patient DRGs (AP DRGs)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/tools/StructureDefinition/resource-information",
"valueString" : "NamingSystem"
}
],
"reference" : {
"reference" : "NamingSystem/APRDRG"
},
"name" : "All Patient Refined Diagnosis Related Groups (APR DRGs)",
"description" : "3M APR DRGs have become the standard across the U.S. for classifying hospital inpatients in non-Medicare populations. As of January 2019, 27 state Medicaid programs use 3M APR DRGs to pay hospitals, as do approximately a dozen commercial payers and Medicaid managed care organizations. Over 2,400 hospitals have licensed 3M APR DRGs to verify payment and analyze their internal operations.\r\n\r\nThe 3M APR DRG methodology classifies hospital inpatients according to their reason for admission, severity of illness and risk of mortality.\r\n\r\nEach year 3M calculates and releases a set of statistics for each 3M APR DRG based on our analysis of large national data sets. These statistics include a relative weight for each 3M APR DRG. The relative weight reflects the average hospital resource use for a patient in that 3M APR DRG relative to the average hospital resource use of all inpatients. Please note that payers and other users of the 3M APR DRG methodology are responsible for ensuring that they use relative weights that are appropriate for their particular populations. The 3M APR DRG statistics also include data for each 3M APR DRG on relative frequency, average length of stay, average charges and incidence of mortality.\r\n\r\n3M APR DRGs can be rolled up into broader categories. The 326 base DRGs roll up into 25 major diagnostic categories (MDCs) plus a pre-MDC category. An example is MDC 04, Diseases and Disorders of the Respiratory System. As well, each 3M APR DRG is assigned to a service line that is consistent with the outpatient service lines that are defined by the 3M⢠Enhanced Ambulatory Patient Groups (EAPGs)."
},
{
"extension" : [
{
&